Skip to content

releng: release-1.36 Code Thaw and milestone applier for 1.37#36782

Merged
k8s-ci-robot merged 2 commits intokubernetes:masterfrom
sreeram-venkitesh:milestone-applier-rules-v1.36
Apr 22, 2026
Merged

releng: release-1.36 Code Thaw and milestone applier for 1.37#36782
k8s-ci-robot merged 2 commits intokubernetes:masterfrom
sreeram-venkitesh:milestone-applier-rules-v1.36

Conversation

@sreeram-venkitesh
Copy link
Copy Markdown
Member

Similar to #36082

Caution: Do not merge before the 1.36.0 official cut is over

  • Lifts 1.36 code freeze for k/k
  • Updates milestone applier for k/* to v1.37

/assign @kubernetes/release-managers
/sig release
/hold

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. sig/release Categorizes an issue or PR as relevant to SIG Release. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/config Issues or PRs related to code in /config sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Apr 10, 2026
@sreeram-venkitesh sreeram-venkitesh changed the title Add milestone applier rules for 1.36 releng: release-1.36 Code Thaw and milestone applier for 1.37 Apr 10, 2026
@dims
Copy link
Copy Markdown
Member

dims commented Apr 10, 2026

/approve

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, sreeram-venkitesh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 10, 2026
@rytswd
Copy link
Copy Markdown
Member

rytswd commented Apr 22, 2026

/unhold

Congrats everyone for the successful v1.36 release!

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 22, 2026
@rytswd
Copy link
Copy Markdown
Member

rytswd commented Apr 22, 2026

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 22, 2026
@k8s-ci-robot k8s-ci-robot merged commit 63c5412 into kubernetes:master Apr 22, 2026
6 checks passed
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

@sreeram-venkitesh: Updated the following 2 configmaps:

  • config configmap in namespace default at cluster test-infra-trusted using the following files:
    • key config.yaml using file config/prow/config.yaml
  • plugins configmap in namespace default at cluster test-infra-trusted using the following files:
    • key plugins.yaml using file config/prow/plugins.yaml
Details

In response to this:

Similar to #36082

Caution: Do not merge before the 1.36.0 official cut is over

  • Lifts 1.36 code freeze for k/k
  • Updates milestone applier for k/* to v1.37

/assign @kubernetes/release-managers
/sig release
/hold

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants